home *** CD-ROM | disk | FTP | other *** search
- Path: ux5.cso.uiuc.edu!djhoward
- From: djhoward@students.uiuc.edu (howard daniel joseph)
- Newsgroups: comp.sys.amiga.misc,comp.sys.amiga.programmer
- Subject: Re: toy operating systems, like AmigaOS
- Followup-To: comp.sys.amiga.misc,comp.sys.amiga.programmer
- Date: 14 Apr 1996 17:46:28 GMT
- Organization: University of Illinois at Urbana
- Message-ID: <4krdlk$jge@vixen.cso.uiuc.edu>
- References: <skllsf.984983.4.5@groomlake.mil>
- NNTP-Posting-Host: ux5.cso.uiuc.edu
- X-Newsreader: TIN [version 1.2 PL2]
-
- Duanne Barry (dbarry@groomlake.mil) wrote:
-
- : I've just spent the last 2 months coding a large and complex algorithm
- : on a Unix box (Sun Sparc 10).
-
- : I've have made hundreds of critical bugs that generally
- : just cause the entire code to blow up (eg. memory overwriting, runaway
- : loops, etc). But never ever did any of my bugs actually crash the Unix box
- : (ie. it never needed a reboot) due to the lovely memory protection.
-
- Well, there are two ways to go about this;
-
- 1) Don't write shitty code.
-
- 2) Write shitty code on a platform that supports shitty code.
-
- 3) If you want to take the shit out of your code without crashing
- a system without memory protection, whack your shit around in a more
- robust environment and then send your shitless code to the Amiga. :)
-
- --
- =====///====================================================================
- ====///=======This message brought to you by djhoward@uiuc.edu==============
- \\\///=========HOME PAGE! http://www.uiuc.edu/ph/www/djhoward ==============
- =\XX/A1200==================================================================
- My views are my own, and not those of my employer or UIUC. Happy Jim?
-